Multi-layer system self-optimization

ABSTRACT

A software-defined network multi-layer controller (SDN-MLC) may communicate with multiple layers of a telecommunication network. The SDN-MLC may have an optimization algorithm that helps manage, in near real-time, the multiple layers of the telecommunication network.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S.patent application Ser. No. 16/022,267, filed Jun. 28, 2018, entitled“MULTI-LAYER SYSTEM SELF-OPTIMIZATION,” the entire contents of which arehereby incorporated herein by reference.

BACKGROUND

A packet layer of the network may include internet protocol (IP) linksconnected among IP devices such as router ports. The IP links may berouted over a path in the optical layer using reconfigurable opticaladd-drop multiplexers (ROADMs) at the endpoints and along the path,transponders at the endpoints, and optical signal regenerators (orrepeaters) in the middle of the path when the path is too long. IPports, optical transponders, and optical regenerators are typicallyassociated with a certain bandwidth unit such as 40 Gbps, 100 Gbps, 200Gbps, or 400 Gbps. If there are N traffic endpoints and K Quality ofService (QoS) classes then the traffic matrix consists of K*N*(N−1)individual traffic units, all of which may change over time and routedover the packet optical network. This disclosure is directed toaddressing self-optimization in an existing network with regard todifferent layers of the network.

SUMMARY

Disclosed herein are techniques that may address repeated joint globaloptimization (e.g., whenever network condition changes) while running amulti-layer network. These network condition changes may be based onscheduled outages (e.g., maintenance activity such as software upgrades)or unscheduled outages (e.g., caused by fiber cuts or failure of IP oroptical devices) or unplanned traffic changes. A software-definednetwork multi-layer controller (SDN-MLC) may communicate with multiplelayers of a telecommunication network. The SDN-MLC may have anoptimization algorithm that helps manage, in near real-time, themultiple layers of the telecommunication network.

In an example, an apparatus (e.g., software-defined network controller)may include a processor and a memory coupled with the processor thateffectuates operations. The operations may include obtaining informationassociated with multiple layers of a telecommunications network, theinformation comprising optical layer information, router layerinformation, and traffic routing information; based on the information,determining to change a configuration of a component of the opticallayer or the router layer; and based on the determination to change theconfiguration of the component of the optical layer or the router layer,providing instructions to effectuate the change. The information shouldbe from multiple layers.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to limitations that solve anyor all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale.

FIG. 1A illustrates an exemplary system for managing multi-layerself-optimization.

FIG. 1B illustrates FIG. 1A in further detail.

FIG. 2 illustrates an exemplary method for managing multi-layer systemself-optimization.

FIG. 3 illustrates an exemplary method for managing multi-layer systemself-optimization.

FIG. 4 illustrates a schematic of an exemplary network device.

FIG. 5 illustrates an exemplary communication system that provideswireless telecommunication services over wireless communicationnetworks.

FIG. 6 is a representation of an exemplary network.

DETAILED DESCRIPTION

Conventional approaches may assume that the mapping between an IP linkand the set of optical transponders and regenerators needed underneathis fixed and if any component fails, the entire IP link fails and thenon-failed components of the IP link are rendered unusable. Also,conventional approaches may assume consideration of traffic routing overthe IP layer and the optical layer separately. Conventionally, opticallayer optimization (e.g., the choice of IP links and their mapping overthe optical layer) may rarely be done (e.g., once) and when opticallayer optimization is done it is usually with a consideration that theIP layer traffic should only be routed over these once-determined set ofIP links.

Disclosed herein are techniques that may address repeated joint globaloptimization (whenever network condition changes) while running amulti-layer network. These network condition changes may be based onscheduled outages (e.g., maintenance activity such as softwareupgrades), unscheduled outages (e.g., caused by fiber cuts or failure ofIP or optical devices), or planned or unplanned traffic changes (e.g.,spike in traffic to an internet resource because of an emergency orwebsite promotion).

FIG. 1A illustrates an exemplary system for near real-timeself-optimization. Software-defined network multi-layer controller 112(SDN-MLC 112) may communicate with multiple layers of system 100 (e.g.,a telecommunication network). SDN-MLC 112 may have an optimizationalgorithm that helps manage, in near real-time, the multiple layers ofthe network. The multiple layers may include optical layer 150, routerlayer 130 (which may also be a switch layer), and multi-protocol labelswitching (MPLS) tunneling layer 120. In another example, layers mayinclude other layers as characterized by the Open SystemsInterconnection model or the like. As generally shown in FIG. 1A (andwith more detail in FIG. 1B), there may be multiple sites, which includeone or more components that help build one or more physical or logicalconnections. For example, in FIG. 1B, for site 101 it may include router131, tail 161, ROADM 151, or regenerator 171 of FIG. 1B). FIG. 1Aillustrates connections between multiple sites as may be seen at eachlevel. Sites include site 101 through site 109. Some sites (e.g., site107) may have optical equipment (ROADM 157), but may not have routingequipment.

FIG. 1B illustrates FIG. 1A in further detail. Optical layer 150 mayinclude multiple components, which are optional based on circumstance,such as reconfigurable optical add-drop multiplexer (ROADMs) (e.g.,ROADM 151-ROADM 159), tails (e.g., tail 161-tail 166), and regenerators(e.g., regenerator 171-regenerator 178). A ROADM is a form of opticaladd-drop multiplexer that adds the ability to remotely switch trafficfrom a wavelength-division multiplexing (WDM) system at the wavelengthlayer. A tail is a connection between an internet protocol (IP) port(e.g., port of router 131) and a transponder port (e.g., port oftransponder 181) that is connected to a ROADM port (e.g., 151). Inoptical fiber communications, a transponder may be the element thatsends and receives the optical signal from a fiber. A transponder istypically characterized by its data rate and the maximum distance thesignal can travel. An optical communications regenerator may be used ina fiber-optic communications system to regenerate an optical signal.Such regenerators may be used to extend the reach of opticalcommunications links by overcoming loss due to attenuation of theoptical fiber. Some regenerators may also correct for distortion of theoptical signal by converting it to an electrical signal, processing thatelectrical signal, and then retransmitting an optical signal. Routerlayer 130 may include routers (e.g., router 131-router 136) or switches(not shown). MPLS layer 120 may have several tunnels logically connectedvia the routers in router layer 130.

FIG. 2 illustrates an exemplary method for near real-timeself-optimization. In an exemplary scenario, as shown in FIG. 1A andFIG. 1B, there may be a system 100 with an optical layer 150, routerlayer 130, and a MPLS layer 120. At step 191, information about eachlayer may be obtained, which may be over seconds, minutes, days, weeks,months, or more. The information may be obtained in near real-time. Thedata may be stored or summarized to reflect seconds, minutes, or hours.This information may be before, during, or subsequent to an outage orother event of system 100 and may be used for forecasting. Theinformation may assist in understanding activity patterns for system100. For example, activity patterns may include the frequency of networklink outages (and flow of traffic activity thereafter), dates and timesof significant traffic load on system 100, minimum or maximum average(or median) traffic load on system 100 during a period, or estimatedtime of repair on a layer (which may be based on similar errors, alarms,or diagnosed issues), among other things. Information may be gathered oneach layer. For MPLS layer 120, the information may include the MPLSinterface state, reserved bandwidth, consumed bandwidth, or labelswitching paths, among other things. For router layer 130, there may beinformation that includes input bytes, output bytes, input packets,output packets, input errors, input drops, input framing errors, outputerrors, output drops, usual traffic load on affected link, types oftraffic on affected link (e.g., defined QoS, video, voice, TCP, UDP,source address, etc.), or routing information, among other things. Therouter layer information may be obtained from one or more routers. Foroptical layer 150, the information may include location of opticalequipment (e.g., transponder 181, regen 171, ROADM 157, or tails),errors from the optical equipment, availability of resources, length ofoptical paths, or outages of the optical equipment, among other things.The optical layer information may be obtained from one more ROADMs.

With continued reference to FIG. 2, based on multi-layer information ofstep 192 (e.g., optical layer and router layer information), there is adetermination whether a change should be conducted on the optical layeror router layer, or on both layers. For example, in this scenario, theload along an optical path site 101-107-106-104 (i.e., path 11) may havereached a threshold (e.g., 80 percent) during a period (e.g., 30 minutetime frame), which may cause errors or latency. A first selected optionmay be for ROADMs along the path (e.g., ROADM 151, ROADM 157, ROADM 156,and ROADM 154) to add one more wavelengths carrying data channels toincrease the capacity along path 11. This may be preferred over changinga routing path at routing layer 130, because there may be a tendency forthe routing protocol to send traffic through router path site 105-104,which actually goes over optical path site 106-104 and doesn't helpresolve the congestion. A second selected option (at a different timewith different weighted info) may be for just the router layer 130 to bechanged. Routes to some or all the traffic may be weighted to go throughone or more routers (e.g., router 132) of site 102, because optical pathsite 102-103-109-104 does not go through optical path site 106-104. Anadditional consideration that may have led for this second selectionoption may be that the ROADMs could not or should not increase itswavelength based on the information as disclosed in step 191. A thirdselected option (at yet a different time with different weighted info)may decide to do a combination of router layer 130 and optical layer 150solutions (e.g., configuration changes) in order to reduce the trafficto an acceptable threshold (e.g., 30 percent). SDN-MLC 112 may be usedto determine the change needed in this step 192. As shown, SDN-MLC 112may obtain data from different sources, such as tail database 114.

At step 193, SDN-MLC 112 may provide instructions based on thedetermination of step 192. For example, SDN-MLC 112 may communicate withrouters, ROADMs, tails, ordering system 115, ROADM SDN controller 110,or the like to execute the determination of step 192. ROADM SDNcontroller 110 may be an intermediate device that may directlycommunicate with optical layer 150 devices. Ordering system 115 may beused to order one or more devices for future use (e.g., spare). Theremay be an anticipated need for the spare based on the information ofstep 191.

SDN-MLC 112 may manage the multiple layers of system 100 in a closedloop and heuristic manner. In a first example, this management may allowfor dynamic mapping between a router layer and an optical layer by usingcolorless or directionless open ROADMs and reusing non-failed routerlayer or optical layer components of a failed link. In a second example,this management may allow for the use of spare tails (connection betweena router port and optical transponder port) and spare opticalregenerators. In a third example, this management by SDN-MLC 112 mayallow router layer devices to be physical or virtual and software andhardware to be aggregated (e.g., traditional routers) or dis-aggregated(e.g., whitebox switches).

Based on the network condition (e.g., traffic matrix or outages)changes, the mapping between IP (e.g., router) and optical layers may bechanged to more efficiently carry traffic under the changed networkcondition. Joint optimization of IP and optical layers whenever thenetwork condition changes may be done by using algorithms based oninteger linear programming or heuristics.

FIG. 3 illustrates an exemplary method for managing multi-layer systemsas disclosed herein. At step 201, initially system 100 may includeunconnected sets of tails and regenerators. Each such tail and opticalregenerator may be classified as spare tails and spare opticalregenerators. The classification and the control of the devices (e.g.,tail and optical regenerator) can be done automatically. For a givennetwork condition, only a selected subset of spare tail pairs may beconnected to form an IP link that carries the required traffic (e.g.,less than 70 percent load) under the required latency constraints (e.g.,5 ms). Depending on the length (e.g., in miles) of a specific IP link,it may require spare optical regenerators as well. At step 202, a jointmulti-layer global optimization may be done to choose the right set ofspare tail pairs (plus optical regenerators, if needed) along with theproper IP layer routing. The joint optimization should satisfyengineering rule constraints (e.g., percentage of traffic of each typeto be carried and latency constraints), use realizable routing (e.g.,shortest path routing, constrained shortest path routing,multi-commodity flow routing with the restriction of equal splitting oftraffic units, etc.), or optimize some other desirable quantities (e.g.,maximizing unused spare tails and regenerators, minimizing the maximumtraffic on a link, etc.). At step 203, SDN-MLC 112 may provideinstructions for IP devices (e.g., physical or virtual routers) oroptical layer devices to be turned up or down depending on networkconditions of system 100.

With continued reference to FIG. 3, at step 204, there may be a detectedchange in network condition that may result in a change in the trafficmatrix and a certain set of tails and regenerators to fail, oralternatively some previously failed tails and regenerators may becomeoperational. At step 205, taking account of the traffic and failureconditions, a new joint multi-layer global optimization may beperformed. The new joint multi-layer global optimization may result insome previously established IP links to be taken down and some new IPlinks to be added and thus also reflecting the dynamic nature andcontrol of the network topology. The joint global optimization problemmay be formulated as an exact integer linear programming problem, but ifthe exact algorithm is time consuming (e.g., hours) then a fastheuristic, which may take seconds or minutes, may be used. At step 206,SDN-MLC 112 may provide instructions for IP devices (e.g., physical orvirtual) or optical layer devices to be turned up or down depending onnetwork conditions of system 100. Software or hardware may remainaggregated or may be disaggregated.

Although a router layer, optical layer, and MPLS tunneling layer arediscussed, it is contemplated that the MPLS tunneling layer be someother tunneling layer or not present at all. Also, it is contemplatedthat the optical layer may be another physical layer other than optical.As discussed herein, the router layer, may be a switching layer or thelike. It is contemplated herein that the term information as consideredherein may be information on any layer (e.g., layer 130 or layer 150).Activity patterns as disclosed herein may be considered “information”which is used in step 192. With reference to estimated time for repair,it is contemplated that sometimes it may take less time to implement arouter layer solution rather than an optical layer solution (or viceversa). Although time may be a significant factor, SDN-MLC 112 mayconsider a predetermined weight of the information in order to derive aweighted determination (e.g., step 192 or step 202). The disclosedtechniques may be used to help change the configuration of devices indifferent layers of the network so that near real-time optimization maymeet the quality of service requirements of the network.

FIG. 4 is a block diagram of network device 300 that may be connected toor comprise a component of system 100 of FIG. 1A. Network device 300 maycomprise hardware or a combination of hardware and software. Thefunctionality to facilitate telecommunications via a telecommunicationsnetwork may reside in one or combination of network devices 300. Networkdevice 300 depicted in FIG. 4 may represent or perform functionality ofan appropriate network device 300, or combination of network devices300, such as, for example, a component or various components of acellular broadcast system wireless network, a processor, a server, agateway, a node, a mobile switching center (MSC), a short messageservice center (SMSC), an automatic location function server (ALFS), agateway mobile location center (GMLC), a radio access network (RAN), aserving mobile location center (SMLC), or the like, or any appropriatecombination thereof. It is emphasized that the block diagram depicted inFIG. 4 is exemplary and not intended to imply a limitation to a specificimplementation or configuration. Thus, network device 300 may beimplemented in a single device or multiple devices (e.g., single serveror multiple servers, single gateway or multiple gateways, singlecontroller or multiple controllers). Multiple network entities may bedistributed or centrally located. Multiple network entities maycommunicate wirelessly, via hard wire, or any appropriate combinationthereof.

Network device 300 may comprise a processor 302 and a memory 304 coupledto processor 302. Memory 304 may contain executable instructions that,when executed by processor 302, cause processor 302 to effectuateoperations associated with mapping wireless signal strength. As evidentfrom the description herein, network device 300 is not to be construedas software per se.

In addition to processor 302 and memory 304, network device 300 mayinclude an input/output system 306. Processor 302, memory 304, andinput/output system 306 may be coupled together (coupling not shown inFIG. 4) to allow communications between them. Each portion of networkdevice 300 may comprise circuitry for performing functions associatedwith each respective portion. Thus, each portion may comprise hardware,or a combination of hardware and software. Accordingly, each portion ofnetwork device 300 is not to be construed as software per se.Input/output system 306 may be capable of receiving or providinginformation from or to a communications device or other network entitiesconfigured for telecommunications. For example input/output system 306may include a wireless communications (e.g., 3G/4G/GPS) card or wiredcommunications (e.g., optical lines) card. Input/output system 306 maybe capable of receiving or sending video information, audio information,control information, image information, data, or any combinationthereof. Input/output system 306 may be capable of transferringinformation with network device 300. In various configurations,input/output system 306 may receive or provide information via anyappropriate means, such as, for example, optical means (e.g., infrared),electromagnetic means (e.g., RF, Wi-Fi, Bluetooth®, ZigBee®), acousticmeans (e.g., speaker, microphone, ultrasonic receiver, ultrasonictransmitter), or a combination thereof.

Input/output system 306 of network device 300 also may contain acommunication connection 308 that allows network device 300 tocommunicate with other devices, network entities, or the like.Communication connection 308 may comprise communication media.Communication media typically embody computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, or wireless media such as acoustic, RF,infrared, or other wireless media. The term computer-readable media asused herein includes both storage media and communication media.Input/output system 306 also may include an input device 310 such askeyboard, mouse, pen, voice input device, or touch input device.Input/output system 306 may also include an output device 312, such as adisplay, speakers, or a printer.

Processor 302 may be capable of performing functions associated withtelecommunications, such as functions for processing broadcast messages,as described herein. For example, processor 302 may be capable of, inconjunction with any other portion of network device 300, determining atype of broadcast message and acting according to the broadcast messagetype or content, as described herein.

Memory 304 of network device 300 may comprise a storage medium having aconcrete, tangible, physical structure. As is known, a signal does nothave a concrete, tangible, physical structure. Memory 304, as well asany computer-readable storage medium described herein, is not to beconstrued as a signal. Memory 304, as well as any computer-readablestorage medium described herein, is not to be construed as a transientsignal. Memory 304, as well as any computer-readable storage mediumdescribed herein, is not to be construed as a propagating signal. Memory304, as well as any computer-readable storage medium described herein,is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 304 may include a volatile storage 314 (such as sometypes of RAM), a nonvolatile storage 316 (such as ROM, flash memory), ora combination thereof. Memory 304 may include additional storage (e.g.,a removable storage 318 or a non-removable storage 320) including, forexample, tape, flash memory, smart cards, CD-ROM, DVD, or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, USB-compatible memory, or any othermedium that can be used to store information and that can be accessed bynetwork device 300. Memory 304 may comprise executable instructionsthat, when executed by processor 302, cause processor 302 to effectuateoperations to map signal strengths in an area of interest.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as processor 302, router 131, and other devices ofFIG. 1A, FIG. 1B, and FIG. 6. In some embodiments, the machine may beconnected (e.g., using a network 502) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient user machine in a server-client user network environment, or as apeer machine in a peer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., acentral processing unit (CPU)), a graphics processing unit (GPU, orboth), a main memory 506 and a static memory 508, which communicate witheach other via a bus 510. The computer system 500 may further include adisplay unit 512 (e.g., a liquid crystal display (LCD), a flat panel, ora solid state display). Computer system 500 may include an input device514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), adisk drive unit 518, a signal generation device 520 (e.g., a speaker orremote control) and a network interface device 522. In distributedenvironments, the embodiments described in the subject disclosure can beadapted to utilize multiple display units 512 controlled by two or morecomputer systems 500. In this configuration, presentations described bythe subject disclosure may in part be shown in a first of display units512, while the remaining portion is presented in a second of displayunits 512.

The disk drive unit 518 may include a tangible computer-readable storagemedium 524 on which is stored one or more sets of instructions (e.g.,software 526) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above.Instructions 526 may also reside, completely or at least partially,within main memory 506, static memory 508, or within processor 504during execution thereof by the computer system 500. Main memory 506 andprocessor 504 also may constitute tangible computer-readable storagemedia.

FIG. 6a is a representation of an exemplary network 600 (e.g., cloud).Network 600 (e.g., system 100) may comprise an SDN—that is, network 600may include one or more virtualized functions implemented on generalpurpose hardware, such as in lieu of having dedicated hardware for everynetwork function. That is, general purpose hardware of network 600 maybe configured to run virtual network elements to support communicationservices, such as mobility services, including consumer services andenterprise services. These services may be provided or measured insessions.

A virtual network functions (VNFs) 602 may be able to support a limitednumber of sessions. Each VNF 602 may have a VNF type that indicates itsfunctionality or role. For example, FIG. 6a illustrates a gateway VNF602 a and a policy and charging rules function (PCRF) VNF 602 b.Additionally or alternatively, VNFs 602 may include other types of VNFs.Each VNF 602 may use one or more virtual machines (VMs) 604 to operate.Each VM 604 may have a VM type that indicates its functionality or role.For example, FIG. 6a illustrates a management control module (MCM) VM604 a, an advanced services module (ASM) VM 604 b, and a DEP VM 604 c.Additionally or alternatively, VMs 604 may include other types of VMs.Each VM 604 may consume various network resources from a hardwareplatform 606, such as a resource 608, a virtual central processing unit(vCPU) 608 a, memory 608 b, or a network interface card (NIC) 608 c.Additionally or alternatively, hardware platform 606 may include othertypes of resources 608.

While FIG. 6a illustrates resources 608 as collectively contained inhardware platform 606, the configuration of hardware platform 606 mayisolate, for example, certain memory 608 c from other memory 608 c.

As described herein, a telecommunications system wherein management andcontrol utilizing a software defined network (SDN), at least in part, onuser equipment, may provide a wireless management and control frameworkthat enables common management and control, such as mobility management,radio resource management, QoS, load balancing, etc., across manytechnologies; decoupling the mobility control from data planes to letthem evolve and scale independently; reducing network state maintainedin the network based on user equipment types to reduce network cost andallow massive scale; shortening cycle time and improving networkupgradability; flexibility in creating end-to-end services based ontypes of user equipment and applications, thus improve customerexperience; or improving user equipment power efficiency and batterylife—especially for simple M2M devices—through enhanced wirelessmanagement.

Crossing or meeting a threshold as discussed herein, which may triggerthe determining step 192, may be described as surpassing a number thatis prescribed in order to determine when some action is triggered. Forexample, a threshold may be crossed if the number of keepalives from adevice is below a certain amount (e.g., 3) within a timeframe (e.g., 10minutes) and therefore an alert may be triggered. In another example, athreshold may be crossed if the number of errors is above a certainamount (e.g., 100) within a certain time frame (e.g., 1 minute) andtherefore an alert may be triggered. In another example, a linkutilization on an IP link crossing a certain threshold may trigger theaction of step 192.

While examples of a telecommunications system in which multi-layerself-optimization may be processed and managed have been described inconnection with various computing devices/processors, the underlyingconcepts may be applied to any computing device, processor, or systemcapable of facilitating a telecommunications system. The varioustechniques described herein may be implemented in connection withhardware or software or, where appropriate, with a combination of both.Thus, the methods and devices may take the form of program code (i.e.,instructions) embodied in concrete, tangible, storage media having aconcrete, tangible, physical structure. Examples of tangible storagemedia include floppy diskettes, CD-ROMs, DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a signal. Acomputer-readable storage medium is not a transient signal. Further, acomputer-readable storage medium is not a propagating signal. Acomputer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes a device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

While a telecommunications system has been described in connection withthe various examples of the various figures, it is to be understood thatother similar implementations may be used or modifications and additionsmay be made to the described examples of a telecommunications systemwithout deviating therefrom. For example, one skilled in the art willrecognize that a telecommunications system as described in the instantapplication may apply to any environment, whether wired or wireless, andmay be applied to any number of such devices connected via acommunications network and interacting across the network. Therefore, atelecommunications system as described herein should not be limited toany single example, but rather should be construed in breadth and scopein accordance with the appended claims.

In describing preferred methods, systems, or apparatuses (e.g., devices)of the subject matter of the present disclosure—multi-layer systemself-optimization—as illustrated in the Figures, specific terminology isemployed for the sake of clarity. The claimed subject matter, however,is not intended to be limited to the specific terminology so selected,and it is to be understood that each specific element includes alltechnical equivalents that operate in a similar manner to accomplish asimilar purpose. In addition, the use of the word “or” is generally usedinclusively unless otherwise provided herein. Real-time as discussedherein refers to operations that usually occur in seconds, but not morethan a minute. As disclosed herein, near real-time events usually occurwithin minutes. A traffic matrix may represent the load from eachingress point to each egress point in an IP network. Although networksare engineered to tolerate some variation in the traffic matrix, largechanges may lead to congested links and poor performance. Configurationchange of a component as disclosed herein may include a software changeor a hardware change (e.g., replace or remove).

This written description uses examples to enable any person skilled inthe art to practice the claimed invention, including making and usingany devices or systems and performing any incorporated methods. Thepatentable scope of the invention is defined by the claims, and mayinclude other examples that occur to those skilled in the art (e.g.,skipping steps, combining steps, or adding steps between exemplarymethods disclosed herein). Such other examples are intended to be withinthe scope of the claims if they have structural elements that do notdiffer from the literal language of the claims, or if they includeequivalent structural elements with insubstantial differences from theliteral languages of the claims.

1. An apparatus comprising: a processor; and a memory coupled with theprocessor, the memory storing executable instructions that when executedby the processor cause the processor to effectuate operationscomprising: obtaining multiple layer information associated withmultiple layers of a telecommunications network, the multiple layerinformation comprising optical layer information and router layerinformation; based on the multiple layer information, determining aconfiguration change of a component of the optical layer or the routerlayer; and based on the determining of the configuration change of thecomponent of the optical layer or the router layer, providinginstructions to effectuate the change of the component.
 2. The apparatusof claim 1, wherein the instructions are provided to a software-definednetwork controller for changing configurations for reconfigurableoptical add-drop multiplexers (ROADMs).
 3. The apparatus of claim 1,wherein the configuration change of the component of the router layercomprises a routing path of traffic in a routing table.
 4. The apparatusof claim 1, wherein the configuration change of the component of theoptical layer comprises a configuration of a tail.
 5. The apparatus ofclaim 1, wherein the configuration change of the component of theoptical layer comprises a configuration of an optical regenerator. 6.The apparatus of claim 1, wherein the configuration change of thecomponent of the optical layer comprises a configuration of areconfigurable optical add-drop multiplexer.
 7. The apparatus of claim1, wherein the configuration change of the component of the opticallayer comprises an addition of a wavelength channel of a reconfigurableoptical add-drop multiplexer.
 8. The apparatus of claim 1, wherein theoptical layer information comprises an outage alarm.
 9. The apparatus ofclaim 1, wherein the optical layer information comprises a load along anoptical path.
 10. A method comprising: obtaining, by a device, multiplelayer information associated with multiple layers of atelecommunications network, the multiple layer information comprisingoptical layer information and router layer information; based on themultiple layer information, determining, by the device, a configurationchange of a component of the optical layer or the router layer; andbased on the determining of the configuration change of the component ofthe optical layer or the router layer, providing, by the device,instructions to effectuate the change of the component.
 11. The methodof claim 10, wherein the instructions are provided to a software-definednetwork controller for changing configurations for reconfigurableoptical add-drop multiplexers (ROADMs).
 12. The method of claim 10,wherein the configuration change of the component of the router layercomprises a routing path of traffic in a routing table.
 13. The methodof claim 10, wherein the configuration change of the component of theoptical layer comprises a configuration of a tail.
 14. The method ofclaim 10, wherein the configuration change of the component of theoptical layer comprises a configuration of an optical regenerator. 15.The method of claim 10, wherein the configuration change of thecomponent of the optical layer comprises a configuration of areconfigurable optical add-drop multiplexer.
 16. The method of claim 10,wherein the configuration change of the component of the optical layercomprises an addition of a wavelength channel of a reconfigurableoptical add-drop multiplexer.
 17. The method of claim 10, wherein theoptical layer information comprises an outage alarm.
 18. The method ofclaim 10, wherein the optical layer information comprises a load alongan optical path.
 19. A system comprising: a reconfigurable opticaladd-drop multiplexer; a router; and a software-defined multi-layercontroller communicatively connected with the router and thereconfigurable optical add-drop multiplexer, the software-definedmulti-layer controller comprising: a processor; and a memory coupledwith the processor, the memory storing executable instructions that whenexecuted by the processor cause the processor to effectuate operationscomprising: obtaining multiple layer information associated withmultiple layers of a telecommunications network, the multiple layerinformation comprising optical layer information; based on the multiplelayer information, determining, by the device, a configuration change ofa component of the optical layer or the router layer; and based on thedetermining of the configuration change of the component of the opticallayer or the router layer, providing, by the device, instructions toeffectuate the change of the component.
 20. The system of claim 19,wherein the optical layer information is obtained from thereconfigurable optical add-drop multiplexer.